Default PUCCH and SRS Beam Determination

ABSTRACT

Apparatuses, systems, and methods for a user equipment device (UE) to determine a default beam for a dedicated PUCCH/SRS in a CC. The UE may determine a pathloss RS has been configured in the CC, e.g., responsive to the UE determining that spatial relationship information for a default transmission beam has not been configured and determine the default beam for transmissions based, at least in part, on the (configured) pathloss RS. Additionally, responsive to determining that the pathloss RS has not been configured in the CC, the UE may determine that no CORESETs/TCI states for a PDSCH in the CC have been configured and determine the default beam for transmissions based, at least in part, on a default transmission beam in another CC, a CC index, a PRACH procedure; a PUSCH transmission; an SRS transmission, and/or a PUCCH transmission.

PRIORITY DATA

This application is the National Stage of International Application No.PCT/CN2019/116181, titled “Default PUCCH and SRS Beam Determination”,filed Nov. 7, 2019, which is hereby incorporated by reference in itsentirety as though fully and completely set forth herein.

FIELD

The present application relates to wireless devices, and moreparticularly to apparatuses, systems, and methods for a wireless deviceto determine a default beam for a dedicated PUCCH and/or an SRS in a CC.

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. In recentyears, wireless devices such as smart phones and tablet computers havebecome increasingly sophisticated. In addition to supporting telephonecalls, many mobile devices now provide access to the internet, email,text messaging, and navigation using the global positioning system(GPS), and are capable of operating sophisticated applications thatutilize these functionalities.

Long Term Evolution (LTE) has become the technology of choice for themajority of wireless network operators worldwide, providing mobilebroadband data and high-speed Internet access to their subscriber base.LTE defines a number of downlink (DL) physical channels, categorized astransport or control channels, to carry information blocks received frommedium access control (MAC) and higher layers. LTE also defines a numberof physical layer channels for the uplink (UL).

For example, LTE defines a Physical Downlink Shared Channel (PDSCH) as aDL transport channel. The PDSCH is the main data-bearing channelallocated to users on a dynamic and opportunistic basis. The PDSCHcarries data in Transport Blocks (TB) corresponding to a MAC protocoldata unit (PDU), passed from the MAC layer to the physical (PHY) layeronce per Transmission Time Interval (TTI). The PDSCH is also used totransmit broadcast information such as System Information Blocks (SIB)and paging messages.

As another example, LTE defines a Physical Downlink Control Channel(PDCCH) as a DL control channel that carries the resource assignment forUEs that are contained in a Downlink Control Information (DCI) message.Multiple PDCCHs can be transmitted in the same subframe using ControlChannel Elements (CCE), each of which is a nine set of four resourceelements known as Resource Element Groups (REG). The PDCCH employsquadrature phase-shift keying (QPSK) modulation, with four QPSK symbolsmapped to each REG. Furthermore, 1, 2, 4, or 8 CCEs can be used for aUE, depending on channel conditions, to ensure sufficient robustness.

Additionally, LTE defines a Physical Uplink Shared Channel (PUSCH) as aUL channel shared by all devices (user equipment, UE) in a radio cell totransmit user data to the network. The scheduling for all UEs is undercontrol of the LTE base station (enhanced Node B, or eNB). The eNB usesthe uplink scheduling grant (DCI format 0) to inform the UE aboutresource block (RB) assignment, and the modulation and coding scheme tobe used. PUSCH typically supports QPSK and quadrature amplitudemodulation (QAM). In addition to user data, the PUSCH also carries anycontrol information necessary to decode the information, such astransport format indicators and multiple-in multiple-out (MIMO)parameters. Control data is multiplexed with information data prior todigital Fourier transform (DFT) spreading.

A proposed next telecommunications standard moving beyond the currentInternational Mobile Telecommunications-Advanced (IMT-Advanced)Standards is called 5th generation mobile networks or 5th generationwireless systems, or 5G for short (otherwise known as 5G-NR for 5G NewRadio, also simply referred to as NR). 5G-NR proposes a higher capacityfor a higher density of mobile broadband users, also supportingdevice-to-device, ultra-reliable, and massive machine communications, aswell as lower latency and lower battery consumption, than current LTEstandards. Further, the 5G-NR standard may allow for less restrictive UEscheduling as compared to current LTE standards. Consequently, effortsare being made in ongoing developments of 5G-NR to take advantage ofhigher throughputs possible at higher frequencies.

SUMMARY

Embodiments relate to apparatuses, systems, and methods for a UE todetermine a default beam for a dedicated PUCCH and/or an SRS in a CC.

In some embodiments, a wireless device, e.g., such as a user equipmentdevice (UE), may be configured to determine whether a pathloss referencesignal (RS) has been configured in a component carrier (CC). In someembodiments, the determination may be responsive to the UE determiningthat spatial relationship information for a default transmission beamhas not been configured by a base station. The UE may determine thedefault beam for transmissions based, at least in part, on the(configured) pathloss RS. In some embodiments, the determination may beresponsive to determining that the pathloss RS has been configured inthe CC. In some embodiments, the default beam for transmissions may bedetermined based, at least in part, on a beam used for a first, last, orindicated pathloss RS in a pathloss RS list. In some embodiments, thepathloss RS list may be configured via radio resource control (RRC)signaling with the base station.

In some embodiments, responsive to determining that the pathloss RS hasnot been configured in the CC, the UE may determine whether any controlresource sets (CORESETs) and/or transmission configuration indication(TCI) states for a physical downlink shared channel (PDSCH) in the CChave been configured by the base station. In some embodiments,responsive to determining that no CORESESTs and/or TCI states have beenconfigured in the CC, the UE may determine the default beam fortransmissions based, at least in part, on a default transmission beam inanother CC, a CC index, a physical random-access channel (PRACH)procedure; a physical uplink shared channel (PUSCH) transmission; asounding reference signal (SRS) transmission, and/or a physical uplinkcontrol channel (PUCCH) transmission.

The techniques described herein may be implemented in and/or used with anumber of different types of devices, including but not limited tocellular phones, tablet computers, wearable computing devices, portablemedia players, and any of various other computing devices.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of various embodiments isconsidered in conjunction with the following drawings, in which:

FIG. 1A illustrates an example wireless communication system accordingto some embodiments.

FIG. 1B illustrates an example of a base station (BS) and an accesspoint in communication with a user equipment (UE) device according tosome embodiments.

FIG. 2 illustrates an example simplified block diagram of a WLAN AccessPoint (AP), according to some embodiments.

FIG. 3 illustrates an example block diagram of a UE according to someembodiments.

FIG. 4 illustrates an example block diagram of a BS according to someembodiments.

FIG. 5 illustrates an example block diagram of cellular communicationcircuitry, according to some embodiments.

FIG. 6A illustrates an example of connections between an EPC network, anLTE base station (eNB), and a 5G NR base station (gNB).

FIG. 6B illustrates an example of a protocol stack for an eNB and a gNB.

FIG. 7A illustrates an example of a 5G network architecture thatincorporates both 3GPP (e.g., cellular) and non-3GPP (e.g.,non-cellular) access to the 5G CN, according to some embodiments.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments.

FIG. 8 illustrates an example of a baseband processor architecture for aUE, according to some embodiments.

FIG. 9 illustrates a flow diagram for a wireless device to determine adefault beam for dedicated PUCCH and/or SRS in a CC in variousimplementations.

FIGS. 10, 11 and 12 illustrate examples of determining a defaulttransmission beam based on a component carrier index, according toembodiments.

FIG. 13 illustrates a flow diagram for a wireless device to determine adefault beam for dedicated PUCCH and/or SRS in a CC, according to someembodiments.

FIG. 14 illustrates a block diagram of an example of a method for awireless device to determine a default beam for dedicated PUCCH and/orSRS in a CC, according to some embodiments.

FIG. 15 illustrates a block diagram of another example of a method for awireless device to determine a default beam for dedicated PUCCH and/orSRS in a CC, according to some embodiments.

While the features described herein may be susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION Terms

The following is a glossary of terms used in this disclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™ Play Station Portable™, Gameboy Advance™,iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices, orother handheld devices, etc. In general, the term “UE” or “UE device”can be broadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element—refers to various elements or combinations ofelements that are capable of performing a function in a device, such asa user equipment or a cellular network device. Processing elements mayinclude, for example: processors and associated memory, portions orcircuits of individual processor cores, entire processor cores,processor arrays, circuits such as an ASIC (Application SpecificIntegrated Circuit), programmable hardware elements such as a fieldprogrammable gate array (FPGA), as well any of various combinations ofthe above.

Channel—a medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” may differ according to different wireless protocols, the term“channel” as used herein may be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthsmay be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE may support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide whileBluetooth channels may be 1 Mhz wide. Other protocols and standards mayinclude different definitions of channels. Furthermore, some standardsmay define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thusthe term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in some embodiments, “approximately” may meanwithin 0.1% of some specified or desired value, while in various otherembodiments, the threshold may be, for example, 2%, 3%, 5%, and soforth, as desired or as required by the particular application.

Concurrent—refers to parallel execution or performance, where tasks,processes, or programs are performed in an at least partiallyoverlapping manner. For example, concurrency may be implemented using“strong” or strict parallelism, where tasks are performed (at leastpartially) in parallel on respective computational elements, or using“weak parallelism”, where the tasks are performed in an interleavedmanner, e.g., by time multiplexing of execution threads.

Various components may be described as “configured to” perform a task ortasks. In such contexts, “configured to” is a broad recitation generallymeaning “having structure that” performs the task or tasks duringoperation. As such, the component can be configured to perform the taskeven when the component is not currently performing that task (e.g., aset of electrical conductors may be configured to electrically connect amodule to another module, even when the two modules are not connected).In some contexts, “configured to” may be a broad recitation of structuregenerally meaning “having circuitry that” performs the task or tasksduring operation. As such, the component can be configured to performthe task even when the component is not currently on. In general, thecircuitry that forms the structure corresponding to “configured to” mayinclude hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

FIGS. 1A and 1B—Communication Systems

FIG. 1A illustrates a simplified example wireless communication system,according to some embodiments. It is noted that the system of FIG. 1 ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102A which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”) and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately bereferred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102Ais implemented in the context of 5G NR, it may alternately be referredto as ‘gNodeB’ or ‘gNB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1, each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations), which may be referred to as “neighboring cells”.Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

In some embodiments, base station 102A may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In someembodiments, a gNB may be connected to a legacy evolved packet core(EPC) network and/or to a NR core (NRC) network. In addition, a gNB cellmay include one or more transition and reception points (TRPs). Inaddition, a UE capable of operating according to 5G NR may be connectedto one or more TRPs within one or more gNBs.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE 106 may alsoor alternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H or DVB-H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

FIG. 1B illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102 and an accesspoint 112, according to some embodiments. The UE 106 may be a devicewith both cellular communication capability and non-cellularcommunication capability (e.g., Bluetooth, Wi-Fi, and so forth) such asa mobile phone, a hand-held device, a computer or a tablet, or virtuallyany type of wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodembodiments described herein by executing such stored instructions.Alternatively, or in addition, the UE 106 may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method embodiments described herein, orany portion of any of the method embodiments described herein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies. In someembodiments, the UE 106 may be configured to communicate using, forexample, CDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD), LTE/LTE-Advanced, or 5G NRusing a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NRusing the single shared radio. The shared radio may couple to a singleantenna, or may couple to multiple antennas (e.g., for MIMO) forperforming wireless communications. In general, a radio may include anycombination of a baseband processor, analog RF signal processingcircuitry (e.g., including filters, mixers, oscillators, amplifiers,etc.), or digital processing circuitry (e.g., for digital modulation aswell as other digital processing). Similarly, the radio may implementone or more receive and transmit chains using the aforementionedhardware. For example, the UE 106 may share one or more parts of areceive and/or transmit chain between multiple wireless communicationtechnologies, such as those discussed above.

In some embodiments, the UE 106 may include separate transmit and/orreceive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, the UE 106 mayinclude one or more radios which are shared between multiple wirelesscommunication protocols, and one or more radios which are usedexclusively by a single wireless communication protocol. For example,the UE 106 might include a shared radio for communicating using eitherof LTE or 5G NR (or LTE or 1×RTTor LTE or GSM), and separate radios forcommunicating using each of Wi-Fi and Bluetooth. Other configurationsare also possible.

FIG. 2—Access Point Block Diagram

FIG. 2 illustrates an exemplary block diagram of an access point (AP)112. It is noted that the block diagram of the AP of FIG. 2 is only oneexample of a possible system. As shown, the AP 112 may includeprocessor(s) 204 which may execute program instructions for the AP 112.The processor(s) 204 may also be coupled (directly or indirectly) tomemory management unit (MMU) 240, which may be configured to receiveaddresses from the processor(s) 204 and to translate those addresses tolocations in memory (e.g., memory 260 and read only memory (ROM) 250) orto other circuits or devices.

The AP 112 may include at least one network port 270. The network port270 may be configured to couple to a wired network and provide aplurality of devices, such as UEs 106, access to the Internet. Forexample, the network port 270 (or an additional network port) may beconfigured to couple to a local network, such as a home network or anenterprise network. For example, port 270 may be an Ethernet port. Thelocal network may provide connectivity to additional networks, such asthe Internet.

The AP 112 may include at least one antenna 234, which may be configuredto operate as a wireless transceiver and may be further configured tocommunicate with UE 106 via wireless communication circuitry 230. Theantenna 234 communicates with the wireless communication circuitry 230via communication chain 232. Communication chain 232 may include one ormore receive chains, one or more transmit chains or both. The wirelesscommunication circuitry 230 may be configured to communicate via Wi-Fior WLAN, e.g., 802.11. The wireless communication circuitry 230 mayalso, or alternatively, be configured to communicate via various otherwireless communication technologies, including, but not limited to, 5GNR, Long-Term Evolution (LTE), LTE Advanced (LTE-A), Global System forMobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000,etc., for example when the AP is co-located with a base station in caseof a small cell, or in other instances when it may be desirable for theAP 112 to communicate via various different wireless communicationtechnologies.

In some embodiments, as further described below, an AP 112 may beconfigured to perform methods to determine a default beam for adedicated PUCCH and/or an SRS in a CC as further described herein.

FIG. 3—Block Diagram of a UE

FIG. 3 illustrates an example simplified block diagram of acommunication device 106, according to some embodiments. It is notedthat the block diagram of the communication device of FIG. 3 is only oneexample of a possible communication device. According to embodiments,communication device 106 may be a user equipment (UE) device, a mobiledevice or mobile station, a wireless device or wireless station, adesktop computer or computing device, a mobile computing device (e.g., alaptop, notebook, or portable computing device), a tablet and/or acombination of devices, among other devices. As shown, the communicationdevice 106 may include a set of components 300 configured to performcore functions. For example, this set of components may be implementedas a system on chip (SOC), which may include portions for variouspurposes. Alternatively, this set of components 300 may be implementedas separate components or groups of components for the various purposes.The set of components 300 may be coupled (e.g., communicatively;directly or indirectly) to various other circuits of the communicationdevice 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector I/F 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andcellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc.,and short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry). In some embodiments, communicationdevice 106 may include wired communication circuitry (not shown), suchas a network interface card, e.g., for Ethernet.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 and 336 as shown. The short to medium range wirelesscommunication circuitry 329 may also couple (e.g., communicatively;directly or indirectly) to one or more antennas, such as antennas 337and 338 as shown. Alternatively, the short to medium range wirelesscommunication circuitry 329 may couple (e.g., communicatively; directlyor indirectly) to the antennas 335 and 336 in addition to, or insteadof, coupling (e.g., communicatively; directly or indirectly) to theantennas 337 and 338. The short to medium range wireless communicationcircuitry 329 and/or cellular communication circuitry 330 may includemultiple receive chains and/or multiple transmit chains for receivingand/or transmitting multiple spatial streams, such as in amultiple-input multiple output (MIMO) configuration.

In some embodiments, as further described below, cellular communicationcircuitry 330 may include dedicated receive chains (including and/orcoupled to, e.g., communicatively; directly or indirectly. dedicatedprocessors and/or radios) for multiple RATs (e.g., a first receive chainfor LTE and a second receive chain for 5G NR). In addition, in someembodiments, cellular communication circuitry 330 may include a singletransmit chain that may be switched between radios dedicated to specificRATs. For example, a first radio may be dedicated to a first RAT, e.g.,LTE, and may be in communication with a dedicated receive chain and atransmit chain shared with an additional radio, e.g., a second radiothat may be dedicated to a second RAT, e.g., 5G NR, and may be incommunication with a dedicated receive chain and the shared transmitchain.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, short to medium range wireless communicationcircuitry 329, cellular communication circuitry 330, connector I/F 320,and/or display 360. The MMU 340 may be configured to perform memoryprotection and page table translation or set up. In some embodiments,the MMU 340 may be included as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Thecommunication device 106 may be configured to perform methods todetermine a default beam for a dedicated PUCCH and/or an SRS in a CC asfurther described herein.

As described herein, the communication device 106 may include hardwareand software components for implementing the above features for acommunication device 106 to communicate a scheduling profile for powersavings to a network. The processor 302 of the communication device 106may be configured to implement part or all of the features describedherein, e.g., by executing program instructions stored on a memorymedium (e.g., a non-transitory computer-readable memory medium).Alternatively (or in addition), processor 302 may be configured as aprogrammable hardware element, such as an FPGA (Field Programmable GateArray), or as an ASIC (Application Specific Integrated Circuit).Alternatively (or in addition) the processor 302 of the communicationdevice 106, in conjunction with one or more of the other components 300,304, 306, 310, 320, 329, 330, 340, 345, 350, 360 may be configured toimplement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, cellular communication circuitry 330 andshort to medium range wireless communication circuitry 329 may eachinclude one or more processing elements. In other words, one or moreprocessing elements may be included in cellular communication circuitry330 and, similarly, one or more processing elements may be included inshort to medium range wireless communication circuitry 329. Thus,cellular communication circuitry 330 may include one or more integratedcircuits (ICs) that are configured to perform the functions of cellularcommunication circuitry 330. In addition, each integrated circuit mayinclude circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of cellular communication circuitry330. Similarly, the short to medium range wireless communicationcircuitry 329 may include one or more ICs that are configured to performthe functions of short to medium range wireless communication circuitry329. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of short to medium range wireless communication circuitry 329.

FIG. 4—Block Diagram of a Base Station

FIG. 4 illustrates an example block diagram of a base station 102,according to some embodiments. It is noted that the base station of FIG.4 is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2.

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some embodiments, base station 102 may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In suchembodiments, base station 102 may be connected to a legacy evolvedpacket core (EPC) network and/or to a NR core (NRC) network. Inaddition, base station 102 may be considered a 5G NR cell and mayinclude one or more transition and reception points (TRPs). In addition,a UE capable of operating according to 5G NR may be connected to one ormore TRPs within one or more gNB s.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430. The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NR.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a 5G NR base station. As another possibility,the base station 102 may include a multi-mode radio which is capable ofperforming communications according to any of multiple wirelesscommunication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTEand UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof. Alternatively(or in addition) the processor 404 of the BS 102, in conjunction withone or more of the other components 430, 432, 434, 440, 450, 460, 470may be configured to implement or support implementation of part or allof the features described herein.

In addition, as described herein, processor(s) 404 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 404. Thus, processor(s) 404 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 404. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 404.

Further, as described herein, radio 430 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 430. Thus, radio 430 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 430. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 430.

FIG. 5: Block Diagram of Cellular Communication Circuitry

FIG. 5 illustrates an example simplified block diagram of cellularcommunication circuitry, according to some embodiments. It is noted thatthe block diagram of the cellular communication circuitry of FIG. 5 isonly one example of a possible cellular communication circuit. Accordingto embodiments, cellular communication circuitry 330 may be included ina communication device, such as communication device 106 describedabove. As noted above, communication device 106 may be a user equipment(UE) device, a mobile device or mobile station, a wireless device orwireless station, a desktop computer or computing device, a mobilecomputing device (e.g., a laptop, notebook, or portable computingdevice), a tablet and/or a combination of devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown (in FIG. 3). In some embodiments,cellular communication circuitry 330 may include dedicated receivechains (including and/or coupled to, e.g., communicatively; directly orindirectly. dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5, cellular communication circuitry 330 mayinclude a modem 510 and a modem 520. Modem 510 may be configured forcommunications according to a first RAT, e.g., such as LTE or LTE-A, andmodem 520 may be configured for communications according to a secondRAT, e.g., such as 5G NR.

As shown, modem 510 may include one or more processors 512 and a memory516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals.For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some embodiments, receive circuitry 532may be in communication with downlink (DL) front end 550, which mayinclude circuitry for receiving radio signals via antenna 335 a.

Similarly, modem 520 may include one or more processors 522 and a memory526 in communication with processors 522. Modem 520 may be incommunication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some embodiments, receive circuitry 542 may be in communicationwith DL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some embodiments, a switch 570 may couple transmit circuitry 534 touplink (UL) front end 572. In addition, switch 570 may couple transmitcircuitry 544 to UL front end 572. UL front end 572 may includecircuitry for transmitting radio signals via antenna 336. Thus, whencellular communication circuitry 330 receives instructions to transmitaccording to the first RAT (e.g., as supported via modem 510), switch570 may be switched to a first state that allows modem 510 to transmitsignals according to the first RAT (e.g., via a transmit chain thatincludes transmit circuitry 534 and UL front end 572). Similarly, whencellular communication circuitry 330 receives instructions to transmitaccording to the second RAT (e.g., as supported via modem 520), switch570 may be switched to a second state that allows modem 520 to transmitsignals according to the second RAT (e.g., via a transmit chain thatincludes transmit circuitry 544 and UL front end 572).

In some embodiments, the cellular communication circuitry 330 may beconfigured to perform methods to determine a default beam for adedicated PUCCH and/or an SRS in a CC as further described herein.

As described herein, the modem 510 may include hardware and softwarecomponents for implementing the above features or for time divisionmultiplexing UL data for NSA NR operations, as well as the various othertechniques described herein. The processors 512 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 512 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 512, in conjunction with one or more of theother components 530, 532, 534, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 512 may include one or moreprocessing elements. Thus, processors 512 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 512. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 512.

As described herein, the modem 520 may include hardware and softwarecomponents for implementing the above features for communicating ascheduling profile for power savings to a network, as well as thevarious other techniques described herein. The processors 522 may beconfigured to implement part or all of the features described herein,e.g., by executing program instructions stored on a memory medium (e.g.,a non-transitory computer-readable memory medium). Alternatively (or inaddition), processor 522 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 522, in conjunction with one or more of theother components 540, 542, 544, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 522 may include one or moreprocessing elements. Thus, processors 522 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 522. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 522.

5G NR Architecture with LTE

In some implementations, fifth generation (5G) wireless communicationwill initially be deployed concurrently with current wirelesscommunication standards (e.g., LTE). For example, dual connectivitybetween LTE and 5G new radio (5G NR or NR) has been specified as part ofthe initial deployment of NR. Thus, as illustrated in FIGS. 6A-B,evolved packet core (EPC) network 600 may continue to communicate withcurrent LTE base stations (e.g., eNB 602). In addition, eNB 602 may bein communication with a 5G NR base station (e.g., gNB 604) and may passdata between the EPC network 600 and gNB 604. Thus, EPC network 600 maybe used (or reused) and gNB 604 may serve as extra capacity for UEs,e.g., for providing increased downlink throughput to UEs. In otherwords, LTE may be used for control plane signaling and NR may be usedfor user plane signaling. Thus, LTE may be used to establish connectionsto the network and NR may be used for data services.

FIG. 6B illustrates a proposed protocol stack for eNB 602 and gNB 604.As shown, eNB 602 may include a medium access control (MAC) layer 632that interfaces with radio link control (RLC) layers 622 a-b. RLC layer622 a may also interface with packet data convergence protocol (PDCP)layer 612 a and RLC layer 622 b may interface with PDCP layer 612 b.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 612 a may interface via a master cell group (MCG) bearer withEPC network 600 whereas PDCP layer 612 b may interface via a splitbearer with EPC network 600.

Additionally, as shown, gNB 604 may include a MAC layer 634 thatinterfaces with RLC layers 624 a-b. RLC layer 624 a may interface withPDCP layer 612 b of eNB 602 via an X2 interface for information exchangeand/or coordination (e.g., scheduling of a UE) between eNB 602 and gNB604. In addition, RLC layer 624 b may interface with PDCP layer 614.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 614 may interface with EPC network 600 via a secondary cellgroup (SCG) bearer. Thus, eNB 602 may be considered a master node (MeNB)while gNB 604 may be considered a secondary node (SgNB). In somescenarios, a UE may be required to maintain a connection to both an MeNBand a SgNB. In such scenarios, the MeNB may be used to maintain a radioresource control (RRC) connection to an EPC while the SgNB may be usedfor capacity (e.g., additional downlink and/or uplink throughput).

5G Core Network Architecture—Interworking with Wi-Fi

In some embodiments, the 5G core network (CN) may be accessed via (orthrough) a cellular connection/interface (e.g., via a 3GPP communicationarchitecture/protocol) and a non-cellular connection/interface (e.g., anon-3GPP access architecture/protocol such as Wi-Fi connection). FIG. 7Aillustrates an example of a 5G network architecture that incorporatesboth 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access tothe 5G CN, according to some embodiments. As shown, a user equipmentdevice (e.g., such as UE 106) may access the 5G CN through both a radioaccess network (RAN, e.g., such as gNB or base station 604) and anaccess point, such as AP 112. The AP 112 may include a connection to theInternet 700 as well as a connection to a non-3GPP inter-workingfunction (N3IWF) 702 network entity. The N3IWF may include a connectionto a core access and mobility management function (AMF) 704 of the 5GCN. The AMF 704 may include an instance of a 5G mobility management (5GMM) function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.As shown, the AMF 704 may include one or more functional entitiesassociated with the 5G CN (e.g., network slice selection function (NSSF)720, short message service function (SMSF) 722, application function(AF) 724, unified data management (UDM) 726, policy control function(PCF) 728, and/or authentication server function (AUSF) 730). Note thatthese functional entities may also be supported by a session managementfunction (SMF) 706 a and an SMF 706 b of the 5G CN. The AMF 706 may beconnected to (or in communication with) the SMF 706 a. Further, the gNB604 may in communication with (or connected to) a user plane function(UPF) 708 a that may also be communication with the SMF 706 a.Similarly, the N3IWF 702 may be communicating with a UPF 708 b that mayalso be communicating with the SMF 706 b. Both UPFs may be communicatingwith the data network (e.g., DN 710 a and 710 b) and/or the Internet 700and IMS core network 710.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments. As shown, a userequipment device (e.g., such as UE 106) may access the 5G CN throughboth a radio access network (RAN, e.g., such as gNB or base station 604or eNB or base station 602) and an access point, such as AP 112. The AP112 may include a connection to the Internet 700 as well as a connectionto the N3IWF 702 network entity. The N3IWF may include a connection tothe AMF 704 of the 5G CN. The AMF 704 may include an instance of the 5GMM function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.In addition, the 5G CN may support dual-registration of the UE on both alegacy network (e.g., LTE via base station 602) and a 5G network (e.g.,via base station 604). As shown, the base station 602 may haveconnections to a mobility management entity (MME) 742 and a servinggateway (SGW) 744. The MME 742 may have connections to both the SGW 744and the AMF 704. In addition, the SGW 744 may have connections to boththe SMF 706 a and the UPF 708 a. As shown, the AMF 704 may include oneor more functional entities associated with the 5G CN (e.g., NSSF 720,SMSF 722, AF 724, UDM 726, PCF 728, and/or AUSF 730). Note that UDM 726may also include a home subscriber server (HSS) function and the PCF mayalso include a policy and charging rules function (PCRF). Note furtherthat these functional entities may also be supported by the SMF 706 aand the SMF 706 b of the 5G CN. The AMF 706 may be connected to (or incommunication with) the SMF 706 a. Further, the gNB 604 may incommunication with (or connected to) the UPF 708 a that may also becommunication with the SMF 706 a. Similarly, the N3IWF 702 may becommunicating with a UPF 708 b that may also be communicating with theSMF 706 b. Both UPFs may be communicating with the data network (e.g.,DN 710 a and 710 b) and/or the Internet 700 and IMS core network 710.

Note that in various embodiments, one or more of the above describednetwork entities may be configured to perform methods to determine adefault beam for a dedicated PUCCH and/or an SRS in a CC, e.g., asfurther described herein.

FIG. 8 illustrates an example of a baseband processor architecture for aUE (e.g., such as UE 106), according to some embodiments. The basebandprocessor architecture 800 described in FIG. 8 may be implemented on oneor more radios (e.g., radios 329 and/or 330 described above) or modems(e.g., modems 510 and/or 520) as described above. As shown, thenon-access stratum (NAS) 810 may include a 5G NAS 820 and a legacy NAS850. The legacy NAS 850 may include a communication connection with alegacy access stratum (AS) 870. The 5G NAS 820 may include communicationconnections with both a 5G AS 840 and a non-3GPP AS 830 and Wi-Fi AS832. The 5G NAS 820 may include functional entities associated with bothaccess stratums. Thus, the 5G NAS 820 may include multiple 5G MMentities 826 and 828 and 5G session management (SM) entities 822 and824. The legacy NAS 850 may include functional entities such as shortmessage service (SMS) entity 852, evolved packet system (EPS) sessionmanagement (ESM) entity 854, session management (SM) entity 856, EPSmobility management (EMM) entity 858, and mobility management (MM)/GPRSmobility management (GMM) entity 860. In addition, the legacy AS 870 mayinclude functional entities such as LTE AS 872, UMTS AS 874, and/orGSM/GPRS AS 876.

Thus, the baseband processor architecture 800 allows for a common 5G-NASfor both 5G cellular and non-cellular (e.g., non-3GPP access). Note thatas shown, the 5G MM may maintain individual connection management andregistration management state machines for each connection.Additionally, a device (e.g., UE 106) may register to a single PLMN(e.g., 5G CN) using 5G cellular access as well as non-cellular access.Further, it may be possible for the device to be in a connected state inone access and an idle state in another access and vice versa. Finally,there may be common 5G-MM procedures (e.g., registration,de-registration, identification, authentication, as so forth) for bothaccesses.

Note that in various embodiments, one or more of the above describedfunctional entities of the 5G NAS and/or 5G AS may be configured toperform methods to determine a default beam for a dedicated PUCCH and/oran SRS in a CC, e.g., as further described herein.

Default Beam for Dedicated PUCCH and/or SRS

In current implementations, a mobile station may determine a defaultbeam for dedicated physical uplink control channel (PUCCH) transmissionsand/or sounding reference signal (SRS) transmissions in a componentcarrier (CC) when at least spatial relation information is configured,e.g. with a base station. Further, in current implementations, themobile station can determine the default beam for dedicated PUCCH and/orSRS when a pathloss reference signal is not configured but a controlresource set (CORESET) and/or transmission configuration indication(TCI) state for a physical downlink shared channel (PDSCH) is configuredin the CC. For example, FIG. 9 illustrates a flow diagram for a wirelessdevice to determine the default beam for dedicated PUCCH and/or SRS in aCC in various implementations. As shown, at 902, the wireless device candetermine whether spatial relationship information is (or has been)configured. At 904, if spatial relationship information is (or has been)configured, the wireless device can determine the default transmissionbeam based on the indicated spatial relationship information. However,at 906, if spatial relationship information is not (or has not been)configured, the wireless device can determine whether a pathlossreference signal is (or has been) configured. Further, at 908, if apathloss reference signal is not (or has not been) configured, thewireless device can determine whether a CORESET/TCI state for a PDSCHhas been configured in the CC. At 910, if the CORESET/TCI state for thePDSCH is (or has been) configured in the CC, the wireless device candetermine the default transmission beam based on a default PDSCH beam.However, the wireless device may be unable to determine a default beamwhen either a pathloss reference signal is (or has been) configured orwhen a pathloss reference signal is not (or has not been) configured anda CORESET/TCI state for a PDSCH is not (or has not been) configured inthe CC as such cases remain undefined in current implementations.

Embodiments described herein provide systems, methods, and mechanismsfor a user equipment device (UE), such as UE 106, to determine a defaultbeam for dedicated PUCCH and/or SRS transmissions in a CC in variousscenarios. In some embodiments, when (if) a pathloss reference signal is(or has been) configured and a spatial relationship is not (or has notbeen) configured, the default beam may be determined based, at least inpart, on a spatial relationship for a dedicated PUCCH/SRS that may bebased, at least in part, on a first, last, and/or indicated pathlossreference signal (RS) in a pathloss RS list configured by (or via) radioresource control (RRC) signaling with a serving base station, such asgNB 604 and/or base station 102. In some embodiments, when (if) apathloss RS is (or has been) configured based on a channel stateinformation reference signal (CSI-RS) and a spatial relationship is not(or has not been) configured, the default beam may be determined based,at least in part, on a spatial relationship for a dedicated PUCCH/SRSthat may be based, at least in part, on a first, last, and/or indicatedpathloss RS in a pathloss RS list configured by (or via) RRC signalingwith a serving base station. In some embodiments, when (if) a pathlossRS is (or has been) configured based on a synchronization signal block(SSB) and a spatial relationship is not (or has not been) configured,the default beam may be determined based, at least in part, on a spatialrelationship for a dedicated PUCCH/SRS that may be based, at least inpart, on a first, last, and/or indicated pathloss RS in a pathloss RSlist configured by (or via) RRC signaling with a serving base station.In some embodiments, the serving base station may configure up to fourpathloss RSs.

In some embodiments, when (if) a pathloss reference signal is (or hasbeen) configured and a spatial relationship is not (or has not been)configured, the default beam may be determined based, at least in part,on a spatial relationship for a dedicated PUCCH/SRS that may be based,at least in part, on a default spatial relationship for a dedicatedPUCCH/SRS when a pathloss RS is not (or has not been) configured and aspatial relationship is not (or has not been) configured. In otherwords, the UE may further consider whether a CORESET/TCI state for aPDSCH in the CC has been configured, e.g., as further described herein.In some embodiments, when (if) a pathloss reference signal is (or hasbeen) configured based on an SSB and a spatial relationship is not (orhas not been) configured, the default beam may be determined based, atleast in part, on a spatial relationship for a dedicated PUCCH/SRS thatmay be based, at least in part, on a default spatial relationship for adedicated PUCCH/SRS when a pathloss RS is not (or has not been)configured and a spatial relationship is not (or has not been)configured. In some embodiments, when (if) a pathloss reference signalis (or has been) configured based on a CSI-RS and a spatial relationshipis not (or has not been) configured, the default beam may be determinedbased, at least in part, on a spatial relationship for a dedicatedPUCCH/SRS that may be based, at least in part, on a default spatialrelationship for a dedicated PUCCH/SRS when a pathloss RS is not (or hasnot been) configured and a spatial relationship is not (or has not been)configured.

In some embodiments, when (if) a pathloss reference signal is not (orhas not been) configured, a spatial relationship is not (or has notbeen) configured, and no CORESET/TCI state for the CC is (or has been)configured, the default beam may be determined based, at least in part,on a default PDSCH beam or a CORESET beam configured in another CC. Insome embodiments, a CC index may be configured via higher layersignaling between the UE and the base station, e.g., such as RRCsignaling or a medium access control (MAC) control element (CE). In someembodiments, a CC index may be selected from CCs within a same band asthe CC, within a same band group as the CC, and/or within a same cellgroup as the CC. In some embodiments, a CC with a monitored CORESETand/or active TCI states configured with lowest and/or highestidentifier (ID) may be selected. In some embodiments, a band group maybe reported by a UE capability, e.g., via RRC signaling and/or a MAC CE.In some embodiments, a CC index may be selected from CCs in a CC groupconfigured by RRC signaling. In some embodiments, a CC with a monitoredCORESET and/or active TCI states configured with a lowest and/or highestID may be selected.

For example, FIGS. 10 to 12 illustrate determining a defaulttransmission beam based on a component carrier index, according toembodiments. As shown in FIG. 10, a base station, such as base station102 and/or gNB 604, may configure multiple component carriers (CC1 toCC4, for example) for a UE, such as UE 106. Thus, for CC1, the UE may beconfigured to not monitor any CORESETs or active TCI states.Additionally, the UE may be configured to monitor a CORESET with an IDof 1 and a TCI state corresponding to a value of 1. Similarly, the UEmay be configured to monitor, for CC2, a CORESET with an ID of 2 and aTCI state corresponding to a value of 2. Further, the UE may beconfigured to monitor, for CC3, a CORESET with an ID of 3 and a TCIstate corresponding to a value of 3, and, for CC4, a CORESET with an IDof 4 and a TCI state corresponding to a value of 4. In addition toconfiguring the UE for each CC, the base station may provide anindication of CC index (e.g., via higher layer signaling, such as RRCsignaling and/or via a MAC CE) to the UE for determination of a defaultbeam. Thus, at 1002, the UE may use the provided CC index to determineto use the CC3 configuration to determine a default transmission beam.

As shown in FIG. 11, a base station, such as base station 102 and/or gNB604, may configure multiple component carriers (CC1 to CC4, for example)for a UE, such as UE 106. Thus, for CC1, the UE may be configured to notmonitor any CORESETs or active TCI states. Additionally, the UE may beconfigured to monitor a CORESET with an ID of 1 and a TCI statecorresponding to a value of 1. Similarly, the UE may be configured tomonitor, for CC2, a CORESET with an ID of 2 and a TCI statecorresponding to a value of 2. Further, the UE may be configured tomonitor, for CC3, a CORESET with an ID of 3 and a TCI statecorresponding to a value of 3, and, for CC4, a CORESET with an ID of 4and a TCI state corresponding to a value of 4. In addition, the UE maydetermine a default beam for transmission, e.g., at 1102, based onvalues of CC indexes. As shown, the UE may select a CC with a monitoredCORESET and/or active TCI state with a lowest ID, e.g., CC 2.

As shown in FIG. 12, a base station, such as base station 102 and/or gNB604, may configure multiple component carriers (CC1 to CC4, for example)for a UE, such as UE 106. Thus, for CC1, the UE may be configured to notmonitor any CORESETs or active TCI states. Additionally, the UE may beconfigured to monitor a CORESET with an ID of 1 and a TCI statecorresponding to a value of 1. Similarly, the UE may be configured tomonitor, for CC2, a CORESET with an ID of 2 and a TCI statecorresponding to a value of 2. Further, the UE may be configured tomonitor, for CC3, a CORESET with an ID of 3 and a TCI statecorresponding to a value of 3, and, for CC4, a CORESET with an ID of 4and a TCI state corresponding to a value of 4. In addition, the UE maydetermine a default beam for transmission, e.g., at 1202, based onvalues of CC indexes. As shown, the UE may select a CC with a monitoredCORESET and/or active TCI state with a highest ID, e.g., CC 4.

In some embodiments, when (if) a pathloss reference signal is not (orhas not been) configured, a spatial relationship is not (or has notbeen) configured, and no CORESET/TCI state for the CC is (or has been)configured, the default beam may be determined based, at least in part,on a scheduling PDCCH for an aperiodic PUCCH/SRS. In some embodiments,when (if) a pathloss reference signal is not (or has not been)configured, a spatial relationship is not (or has not been) configured,and no CORESET/TCI state for the CC is (or has been) configured, thedefault beam may be determined based, at least in part, on a beam usedfor a most recent random access channel (RACH) procedure in the CC or inany CC in the same band as the CC, the same band group as the CC, in thesame cell group as the CC, and/or in a same CC list group as the CC. Insome embodiments, when (if) a pathloss reference signal is not (or hasnot been) configured, a spatial relationship is not (or has not been)configured, and no CORESET/TCI state for the CC is (or has been)configured, the default beam may be determined based, at least in part,on a beam used for a most recent transmission of PUSCH, PUCCH, and/orSRS in the CC or in any CC in the same band as the CC, same band groupas the CC, the same cell group as the CC, and/or in a same CC list groupas the CC. In some embodiments, the CC list group may be configured viahigher layer signaling, e.g., such as RRC signaling and/or a MAC CE.

In some embodiments, when (if) a pathloss reference signal is not (orhas not been) configured, a spatial relationship is not (or has notbeen) configured, and no CORESET/TCI state for the CC is (or has been)configured, a pathloss RS for power control for a dedicated PUCCH and/orSRS may be based, at least in part, on a downlink RS used to determine adefault spatial relationship, e.g., as described herein. In someembodiments, when (if) a default spatial relationship is changed, anapplicable time for a new pathloss RS may be a specified number of timeslots (e.g., 1, 2, 5, 10, and so forth)time slot after the UE measures“N” samples of the pathloss RS after corresponding control signaling fora spatial relationship update takes effect. In some embodiments, “N” maybe configured by higher layer signaling, may be based on a UEcapability, and/or may be predefined (e.g., via a standard). In someembodiments, when (if) a default spatial relation is changed, aneffective time for a new pathloss RS may be the same as a new spatialrelationship. In some embodiments, prior to an effective time of a newpathloss RS, the UE may use a higher layer filtered RSRP based on aprior pathloss RS for pathloss measurement. In some embodiments, priorto an effective time of a new pathloss RS, the UE may use an L1-RSRPbased on the new pathloss RS for pathloss measurement.

In some embodiments, when (if) a pathloss reference signal is not (orhas not been) configured, a spatial relationship is not (or has notbeen) configured, and no CORESET/TCI state for the CC is (or has been)configured, a pathloss RS for power control for a dedicated PUCCH and/orSRS may be based, at least in part, on an SSB associated with a mostrecent RACH procedure in the CC or in any CC in the same band as the CC,the same band group as the CC, and/or in the same cell group as the CC.In some embodiments, the band group may be reported by UE as a UEcapability. In some embodiments, the CC list group may be configured viahigher layer signaling, e.g., such as RRC signaling and/or a MAC CE.

In some embodiments, when (if) a pathloss reference signal is not (orhas not been) configured, a spatial relationship is not (or has notbeen) configured, and no CORESET/TCI state for the CC is (or has been)configured, a pathloss RS for power control for a dedicated PUCCH and/orSRS may be based, at least in part, on a pathloss RS used for a mostrecent transmission of PUSCH, PUCCH, and/or SRS in the CC or in any CCin the same band as the CC, the same band group as the CC, in the samecell group as the CC, and/or in the same CC list group as the CC. Insome embodiments, the band group may be reported by UE as a UEcapability. In some embodiments, the CC list group may be configured viahigher layer signaling, e.g., such as RRC signaling and/or a MAC CE.

FIG. 13 illustrates a flow diagram for a wireless device to determine adefault beam for dedicated PUCCH and/or SRS in a CC, according to someembodiments. The flow diagram shown in FIG. 13 may be used inconjunction with any of the systems, methods, or devices shown in theFigures, among other devices. In various embodiments, some of theelements shown may be performed concurrently, in a different order thanshown, or may be omitted. Additional elements may also be performed asdesired. As shown, this method may operate as follows.

At 1302, a UE, such as UE 106, may determine whether spatialrelationship information for a default transmission beam has beenconfigured, e.g., via signaling with a base station, such as basestation 102 and/or gNB 604. At 1304, when the spatial relationshipinformation for the default transmission beam has been configured, theUE may determine the default transmission beam based on the indicatedspatial relationship information.

At 1306, in response to determining that the spatial relationshipinformation for the default transmission beam has not been configured,the UE may determine whether a pathloss RS has been configured. At 1312,in response to determining that the pathloss RS has been configured, theUE may determine the default transmission beam (e.g., for dedicatedPUCCH and/or SRS transmission in a CC) based on a CSI-RS and/or an SSBcorresponding to the pathloss RS, e.g., as described herein. Forexample, in some embodiments, the default transmission beam may bedetermined based on a first, last, and/or indicated pathloss RS in apathloss RS list configured by (or via) RRC signaling with the basestation.

At 1308, in response to determining that a pathloss RS has not beenconfigured, the UE may determine whether any CORESETs and/or TCI stateshave been configured in the CC. At 1310, when a CORESET and/or TCI statehas been configured in the CC, the UE may determine the defaulttransmission beam based on a default PDSCH beam.

At 1314, in response to determining that no CORESETs and/or TCI stateshave been configured in the CC, the UE may determine the defaulttransmission beam (e.g., for dedicated PUCCH and/or SRS transmission ina CC) based on a default beam from another CC, a recent transmissionfrom a PRACH procedure, a recent PUSCH transmission, a recent SRStransmission, and/or a recent PUCCH transmission. For example, in someembodiments, the default transmission beam may be determined based, atleast in part, on a default PDSCH beam or a CORESET beam configured inanother CC. As another example, in some embodiments, the defaulttransmission beam may be determined based, at least in part, on ascheduling PDCCH for an aperiodic PUCCH/SRS. As a further example, insome embodiments, the default transmission beam may be determined based,at least in part, on a beam used for a most recent PRACH procedure inthe CC or in any CC in the same band as the CC, the same band group asthe CC, in the same cell group as the CC, and/or in a same CC list groupas the CC. As yet another example, in some embodiments, the defaulttransmission beam may be determined based, at least in part, on a beamused for a most recent transmission of PUSCH, PUCCH, and/or SRS in theCC or in any CC in the same band as the CC, same band group as the CC,the same cell group as the CC, and/or in a same CC list group as the CC.In some embodiments, a CC index may be configured via higher layersignaling between the UE and the base station, e.g., such as RRCsignaling or a medium access control (MAC) control element (CE). In someembodiments, a CC index may be selected from CCs within a same band asthe CC, within a same band group as the CC, and/or within a same cellgroup as the CC. In some embodiments, a CC with a monitored CORESETand/or active TCI states configured with lowest and/or highestidentifier (ID) may be selected. In some embodiments, a band group maybe reported by a UE capability, e.g., via RRC signaling and/or a MAC CE.In some embodiments, a CC index may be selected from CCs in a CC groupconfigured by RRC signaling. In some embodiments, a CC with a monitoredCORESET and/or active TCI states configured with a lowest and/or highestID may be selected.

FIG. 14 illustrates a block diagram of an example of a method for awireless device to determine a default beam for dedicated PUCCH and/orSRS in a CC, according to some embodiments. The method shown in FIG. 14may be used in conjunction with any of the systems, methods, or devicesshown in the Figures, among other devices. In various embodiments, someof the method elements shown may be performed concurrently, in adifferent order than shown, or may be omitted. Additional methodelements may also be performed as desired. As shown, this method mayoperate as follows.

At 1402, a UE, such as UE 106, may determine whether a pathlossreference signal (RS) has been configured in a component carrier (CC).In some embodiments, the determination may be responsive to the UEdetermining that spatial relationship information for a defaulttransmission beam has not been configured by a base station, such asbase station 102 and/or gNB 604, serving the UE.

At 1404, the UE may determine the default beam for transmissions based,at least in part, on the (configured) pathloss RS. In some embodiments,the determination may be responsive to determining that the pathloss RShas been configured in the CC. In some embodiments, the default beam fortransmissions may be determined based, at least in part, on a beam usedfor a first, last, or indicated pathloss RS in a pathloss RS list. Insome embodiments, the pathloss RS list may be configured via radioresource control (RRC) signaling with the base station.

In some embodiments, responsive to determining that the pathloss RS hasnot been configured in the CC, the UE may determine whether any controlresource sets (CORESETs) and/or transmission configuration indication(TCI) states for a physical downlink shared channel (PDSCH) in the CChave been configured by the base station. In some embodiments,responsive to determining that no CORESESTs and/or TCI states have beenconfigured in the CC, the UE may determine the default beam fortransmissions based, at least in part, on a default transmission beam inanother CC, a CC index, a physical random-access channel (PRACH)procedure; a physical uplink shared channel (PUSCH) transmission; asounding reference signal (SRS) transmission, and/or a physical uplinkcontrol channel (PUCCH) transmission.

In some embodiments, to determine the default beam for transmissionsbased, at least in part, on a default transmission beam in another CC,the UE may determine the default beam for transmissions based, at leastin part, on a default physical downlink shared channel (PDSCH) beam or aCORESET beam configured in another CC. In some embodiments, to determinethe default beam for transmissions based, at least in part, on a PRACHprocedure, the UE may determine the default beam for transmissionsbased, at least in part, on a beam used for a most recent PRACHprocedure in the CC, in a CC in a same band as the CC, in a same bandgroup as the CC, in a same cell group as the CC, and/or in a same CClist group as the CC. In some embodiments, to determine the default beamfor transmissions based, at least in part, on a PUSCH transmission, theUE may determine the default beam for transmissions based, at least inpart, on a beam used for a most recent PUSCH transmission in the CC, ina CC in a same band as the CC, in a same band group as the CC, in a samecell group as the CC, and/or in a same CC list group as the CC. In someembodiments, to determine the default beam for transmissions based, atleast in part, on an SRS transmission, the UE may determine the defaultbeam for transmissions based, at least in part, on a beam used for amost recent SRS transmission in the CC, in a CC in a same band as theCC, in a same band group as the CC, in a same cell group as the CC,and/or in a same CC list group as the CC. In some embodiments, todetermine the default beam for transmissions based, at least in part, ona PUCCH transmission, the UE may determine the default beam fortransmissions based, at least in part, on a beam used for a most recentPUCCH transmission in the CC, in a CC in a same band as the CC, in asame band group as the CC, in a same cell group as the CC, and/or in asame CC list group as the CC. In some embodiments, to determine thedefault beam for transmissions based, at least in part, on a CC index,the UE may determine the default beam for transmissions based, at leastin part, on selection of a CC index from CCs within a same band as theCC, within a same band group as the CC, and/or within a same cell groupas the CC.

In some embodiments, the UE may report the band group to the basestation via a UE capability message. In some embodiments, selection of aCC index may include selection of a monitored CORESET and/or active TCIstate configured with a lowest or highest identifier. In someembodiments, selection of a CC index may include selection of a CC indexfrom CCs in a CC group configured by radio resource control (RRC)signaling with the base station.

In some embodiments, responsive to determining that the pathloss RS hasnot been configured in the CC, the UE may determine whether any controlresource sets (CORESETs) and/or transmission configuration indication(TCI) states for a physical downlink shared channel (PDSCH) in the CChave been configured by the base station. In some embodiments,responsive to determining that no CORESESTs and/or TCI states have beenconfigured in the CC, the UE may determine a pathloss RS for powercontrol for a dedicated physical uplink control channel (PUCCH) or asounding reference signal (SRS) based, at least in part, on a downlinkRS used to determine a default spatial relationship, a synchronizationsignal block (SSB) associated with a most recent random-access channel(RACH) procedure in the CC, in a CC in a same band as the CC, in a CC ina same band group as the CC, and/or in a CC in a same cell group as theCC, a pathloss RS used for a most recent transmission on a physicaluplink shared channel (PUSCH) in the CC, in a CC in a same band as theCC, in a CC in a same band group as the CC, and/or in a CC in a samecell group as the CC, a pathloss RS used for a most recent transmissionof a physical uplink control channel (PUCCH) in the CC, in a CC in asame band as the CC, in a CC in a same band group as the CC, and/or in aCC in a same cell group as the CC, and/or a pathloss RS used for a mostrecent transmission of an SRS in the CC, in a CC in a same band as theCC, in a CC in a same band group as the CC, and/or in a CC in a samecell group as the CC.

In some embodiments, the UE may determine a change in a default spatialrelationship and switch to a new pathloss RS one time slot aftermeasuring a specified number of samples of the new pathloss RS aftercorresponding control signaling for a spatial relationship update takeseffect. In some embodiments, the specified number of samples ispredefined via a standard, configured via higher layer signaling withthe base station, and/or based on capabilities of the apparatus. In someembodiments, after determining the change in the default spatialrelationship and prior to an effective time of the new pathloss RS, theUE may use a higher layer filtered reference signal received power(RSRP) based on a prior pathloss RS and/or a layer 1 (L1) RSRP based onthe new pathloss RS for pathloss measurement.

FIG. 15 illustrates a block diagram of another example of a method for awireless device to determine a default beam for dedicated PUCCH and/orSRS in a CC, according to some embodiments. The method shown in FIG. 15may be used in conjunction with any of the systems, methods, or devicesshown in the Figures, among other devices. In various embodiments, someof the method elements shown may be performed concurrently, in adifferent order than shown, or may be omitted. Additional methodelements may also be performed as desired. As shown, this method mayoperate as follows.

At 1502, a UE, such as UE 106, may determine whether a pathlossreference signal (RS) has been configured in a component carrier (CC).In some embodiments, the determination may be responsive to the UEdetermining that spatial relationship information for a defaulttransmission beam has not been configured by a base station, such asbase station 102 and/or gNB 604, serving the UE.

At 1504, responsive to determining that the pathloss RS has not beenconfigured in the CC, the UE may determine whether any control resourcesets (CORESETs) and/or transmission configuration indication (TCI)states for a physical downlink shared channel (PDSCH) in the CC havebeen configured by the base station.

At 1506, responsive to determining that no CORESESTs and/or TCI stateshave been configured in the CC, the UE may determine the default beamfor transmissions based, at least in part, on a default transmissionbeam in another CC, a CC index, a physical random-access channel (PRACH)procedure; a physical uplink shared channel (PUSCH) transmission; asounding reference signal (SRS) transmission, and/or a physical uplinkcontrol channel (PUCCH) transmission.

In some embodiments, to determine the default beam for transmissionsbased, at least in part, on a default transmission beam in another CC,the UE may determine the default beam for transmissions based, at leastin part, on a default physical downlink shared channel (PDSCH) beam or aCORESET beam configured in another CC. In some embodiments, to determinethe default beam for transmissions based, at least in part, on a PRACHprocedure, the UE may determine the default beam for transmissionsbased, at least in part, on a beam used for a most recent PRACHprocedure in the CC, in a CC in a same band as the CC, in a same bandgroup as the CC, in a same cell group as the CC, and/or in a same CClist group as the CC. In some embodiments, to determine the default beamfor transmissions based, at least in part, on a PUSCH transmission, theUE may determine the default beam for transmissions based, at least inpart, on a beam used for a most recent PUSCH transmission in the CC, ina CC in a same band as the CC, in a same band group as the CC, in a samecell group as the CC, and/or in a same CC list group as the CC. In someembodiments, to determine the default beam for transmissions based, atleast in part, on an SRS transmission, the UE may determine the defaultbeam for transmissions based, at least in part, on a beam used for amost recent SRS transmission in the CC, in a CC in a same band as theCC, in a same band group as the CC, in a same cell group as the CC,and/or in a same CC list group as the CC. In some embodiments, todetermine the default beam for transmissions based, at least in part, ona PUCCH transmission, the UE may determine the default beam fortransmissions based, at least in part, on a beam used for a most recentPUCCH transmission in the CC, in a CC in a same band as the CC, in asame band group as the CC, in a same cell group as the CC, and/or in asame CC list group as the CC. In some embodiments, to determine thedefault beam for transmissions based, at least in part, on a CC index,the UE may determine the default beam for transmissions based, at leastin part, on selection of a CC index from CCs within a same band as theCC, within a same band group as the CC, and/or within a same cell groupas the CC.

In some embodiments, the UE may report the band group to the basestation via a UE capability message. In some embodiments, selection of aCC index may include selection of a monitored CORESET and/or active TCIstate configured with a lowest or highest identifier. In someembodiments, selection of a CC index may include selection of a CC indexfrom CCs in a CC group configured by radio resource control (RRC)signaling with the base station.

In some embodiments, the UE may determine the default beam fortransmissions based, at least in part, on the (configured) pathloss RS.In some embodiments, the determination may be responsive to determiningthat the pathloss RS has been configured in the CC. In some embodiments,the default beam for transmissions may be determined based, at least inpart, on a beam used for a first, last, or indicated pathloss RS in apathloss RS list. In some embodiments, the pathloss RS list may beconfigured via radio resource control (RRC) signaling with the basestation.

In some embodiments, responsive to determining that the pathloss RS hasnot been configured in the CC, the UE may determine whether any controlresource sets (CORESETs) and/or transmission configuration indication(TCI) states for a physical downlink shared channel (PDSCH) in the CChave been configured by the base station. In some embodiments,responsive to determining that no CORESESTs and/or TCI states have beenconfigured in the CC, the UE may determine a pathloss RS for powercontrol for a dedicated physical uplink control channel (PUCCH) or asounding reference signal (SRS) based, at least in part, on a downlinkRS used to determine a default spatial relationship, a synchronizationsignal block (SSB) associated with a most recent random-access channel(RACH) procedure in the CC, in a CC in a same band as the CC, in a CC ina same band group as the CC, and/or in a CC in a same cell group as theCC, a pathloss RS used for a most recent transmission on a physicaluplink shared channel (PUSCH) in the CC, in a CC in a same band as theCC, in a CC in a same band group as the CC, and/or in a CC in a samecell group as the CC, a pathloss RS used for a most recent transmissionof a physical uplink control channel (PUCCH) in the CC, in a CC in asame band as the CC, in a CC in a same band group as the CC, and/or in aCC in a same cell group as the CC, and/or a pathloss RS used for a mostrecent transmission of an SRS in the CC, in a CC in a same band as theCC, in a CC in a same band group as the CC, and/or in a CC in a samecell group as the CC.

In some embodiments, the UE may determine a change in a default spatialrelationship and switch to a new pathloss RS one time slot aftermeasuring a specified number of samples of the new pathloss RS aftercorresponding control signaling for a spatial relationship update takeseffect. In some embodiments, the specified number of samples ispredefined via a standard, configured via higher layer signaling withthe base station, and/or based on capabilities of the apparatus. In someembodiments, after determining the change in the default spatialrelationship and prior to an effective time of the new pathloss RS, theUE may use a higher layer filtered reference signal received power(RSRP) based on a prior pathloss RS and/or a layer 1 (L1) RSRP based onthe new pathloss RS for pathloss measurement.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Embodiments of the present disclosure may be realized in any of variousforms. For example, some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of the methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a device (e.g., a UE 106) may be configured toinclude a processor (or a set of processors) and a memory medium, wherethe memory medium stores program instructions, where the processor isconfigured to read and execute the program instructions from the memorymedium, where the program instructions are executable to implement anyof the various method embodiments described herein (or, any combinationof the method embodiments described herein, or, any subset of any of themethod embodiments described herein, or, any combination of suchsubsets). The device may be realized in any of various forms.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

What is claimed is:
 1. A user equipment device (UE), comprising: atleast one antenna; at least one radio, wherein the at least one radio isconfigured to perform cellular communication using at least one radioaccess technology (RAT); one or more processors coupled to the at leastone radio, wherein the one or more processors and the at least one radioare configured to perform voice and/or data communications; wherein theone or more processors are configured to cause the UE to: in response todetermining that a base station serving the UE has not configuredspatial relationship information for a default beam for transmissions ina component carrier (CC), determine whether a pathloss reference signal(RS) has been configured in the CC; and in response to determining thatthe pathloss RS has been configured in the CC, determine the defaultbeam for transmissions based, at least in part, on the pathloss RS. 2.The UE of claim 1, wherein the one or more processors are furtherconfigured to cause the UE to: in response to determining that thepathloss RS has not been configured in the CC, determine whether anycontrol resource sets (CORESETs) and/or transmission configurationindication (TCI) states for a physical downlink shared channel (PDSCH)in the CC have been configured; and in response to determining that noCORESESTs and/or TCI states have been configured in the CC, determinethe default beam for transmissions based, at least in part, on at leastone of: a default transmission beam in another CC; a CC index; aphysical random-access channel (PRACH) procedure; a physical uplinkshared channel (PUSCH) transmission; a sounding reference signal (SRS)transmission; or a physical uplink control channel (PUCCH) transmission.3. The UE of claim 2, wherein, to determine the default beam fortransmissions based, at least in part, on a default transmission beam inanother CC, the one or more processors are further configured to causethe UE to determine the default beam for transmissions based, at leastin part, on a default physical downlink shared channel (PDSCH) beam or aCORESET beam configured in another CC.
 4. The UE of claim 2, wherein, todetermine the default beam for transmissions based, at least in part, ona PRACH procedure, the one or more processors are further configured tocause the UE to determine the default beam for transmissions based, atleast in part, on a beam used for a most recent PRACH procedure in theCC, in a CC in a same band as the CC, in a same band group as the CC, ina same cell group as the CC, or in a same CC list group as the CC;wherein, to determine the default beam for transmissions based, at leastin part, on a PUSCH transmission, the one or more processors are furtherconfigured to cause the UE to determine the default beam fortransmissions based, at least in part, on a beam used for a most recentPUSCH transmission in the CC, in a CC in a same band as the CC, in asame band group as the CC, in a same cell group as the CC, or in a sameCC list group as the CC; wherein, to determine the default beam fortransmissions based, at least in part, on an SRS transmission, the oneor more processors are further configured to cause the UE to determinethe default beam for transmissions based, at least in part, on a beamused for a most recent SRS transmission in the CC, in a CC in a sameband as the CC, in a same band group as the CC, in a same cell group asthe CC, or in a same CC list group as the CC; and wherein, to determinethe default beam for transmissions based, at least in part, on a PUCCHtransmission, the one or more processors are further configured to causethe UE to determine the default beam for transmissions based, at leastin part, on a beam used for a most recent PUCCH transmission in the CC,in a CC in a same band as the CC, in a same band group as the CC, in asame cell group as the CC, or in a same CC list group as the CC.
 5. TheUE of claim 4, wherein the one or more processors are further configuredto cause the UE to: report, to the base station, the band group via a UEcapability message.
 6. The UE of claim 2, wherein, to determine thedefault beam for transmissions based, at least in part, on a CC index,the one or more processors are further configured to cause the UE todetermine the default beam for transmissions based, at least in part, onselection of a CC index from CCs within a same band as the CC, within asame band group as the CC, or within a same cell group as the CC.
 7. TheUE of claim 6, wherein selection of a CC index includes selection of amonitored CORESET and/or active TCI state configured with a lowest orhighest identifier.
 8. The UE of claim 6, wherein selection of a CCindex includes selection of a CC index from CCs in a CC group configuredby radio resource control (RRC) signaling with the base station.
 9. TheUE of claim 1, wherein, to determine the default beam for transmissionsbased, at least in part, on the pathloss RS, the one or more processorsare further configured to cause the UE to determine the default beam fortransmissions based, at least in part, on a beam used for a first, last,or indicated pathloss RS in a pathloss RS list configured via radioresource control (RRC) signaling with the base station.
 10. Anapparatus, comprising: a memory; and a processing element incommunication with the memory, wherein the processing element isconfigured to: in response to determining that a base station has notconfigured spatial relationship information for a default beam fortransmissions in a component carrier (CC), determine whether a pathlossreference signal (RS) has been configured in the CC; and in response todetermining that the pathloss RS has been configured in the CC,determine the default beam for transmissions based, at least in part, onthe pathloss RS.
 11. The apparatus of claim 10, wherein the processingelement is further configured to: in response to determining that thepathloss RS has not been configured in the CC, determine whether anycontrol resource sets (CORESETs) and/or transmission configurationindication (TCI) states for a physical downlink shared channel (PDSCH)in the CC have been configured; and in response to determining that noCORESESTs and/or TCI states have been configured in the CC, determine apathloss RS for power control for a dedicated physical uplink controlchannel (PUCCH) or a sounding reference signal (SRS) based, at least inpart, on at least one of: a downlink RS used to determine a defaultspatial relationship; a synchronization signal block (SSB) associatedwith a most recent random-access channel (RACH) procedure in the CC, ina CC in a same band as the CC, in a CC in a same band group as the CC,or in a CC in a same cell group as the CC; a pathloss RS used for a mostrecent transmission on a physical uplink shared channel (PUSCH) in theCC, in a CC in a same band as the CC, in a CC in a same band group asthe CC, or in a CC in a same cell group as the CC; a pathloss RS usedfor a most recent transmission of a physical uplink control channel(PUCCH) in the CC, in a CC in a same band as the CC, in a CC in a sameband group as the CC, or in a CC in a same cell group as the CC; or apathloss RS used for a most recent transmission of an SRS in the CC, ina CC in a same band as the CC, in a CC in a same band group as the CC,or in a CC in a same cell group as the CC.
 12. The apparatus of claim11, wherein the processing element is further configured to: determine achange in a default spatial relationship; and switch to a new pathlossRS one time slot after measuring a specified number of samples of thenew pathloss RS after corresponding control signaling for a spatialrelationship update takes effect.
 13. The apparatus of claim 12, whereinthe specified number of samples is predefined via a standard, configuredvia higher layer signaling with the base station, or based oncapabilities of the apparatus.
 14. The apparatus of claim 12, wherein,after determining the change in the default spatial relationship andprior to an effective time of the new pathloss RS, the processingelement is further configured to use a higher layer filtered referencesignal received power (RSRP) based on a prior pathloss RS or a layer 1(L1) RSRP based on the new pathloss RS for pathloss measurement.
 15. Theapparatus of claim 11, wherein the processing element is furtherconfigured to: in response to determining that the pathloss RS has notbeen configured in the CC, determine whether any control resource sets(CORESETs) and/or transmission configuration indication (TCI) states fora physical downlink shared channel (PDSCH) in the CC have beenconfigured; and in response to determining that no CORESESTs and/or TCIstates have been configured in the CC, determine the default beam fortransmissions based, at least in part, on at least one of: a defaulttransmission beam in another CC; a CC index; a physical random-accesschannel (PRACH) procedure; a physical uplink shared channel (PUSCH)transmission; a sounding reference signal (SRS) transmission; or aphysical uplink control channel (PUCCH) transmission.
 16. Anon-transitory computer readable memory medium storing programinstructions executable by processing circuitry to cause a userequipment device (UE) to: in response to determining that a base stationserving the UE has not configured spatial relationship information for adefault beam for transmissions in a component carrier (CC), determinewhether a pathloss reference signal (RS) has been configured in the CC;in response to determining that the pathloss RS has not been configuredin the CC, determine whether any control resource sets (CORESETs) and/ortransmission configuration indication (TCI) states for a physicaldownlink shared channel (PDSCH) in the CC have been configured; and inresponse to determining that no CORESESTs and/or TCI states have beenconfigured in the CC, determine the default beam for transmissionsbased, at least in part, on at least one of: a default transmission beamin another CC; a CC index; a physical random-access channel (PRACH)procedure; a physical uplink shared channel (PUSCH) transmission; asounding reference signal (SRS) transmission; or a physical uplinkcontrol channel (PUCCH) transmission.
 17. The non-transitory computerreadable memory medium of claim 16, wherein the program instructions arefurther executable to cause the UE to: in response to determining thatthe pathloss RS has been configured in the CC, determine the defaultbeam for transmissions based, at least in part, on the pathloss RS. 18.The non-transitory computer readable memory medium of claim 17, wherein,to determine the default beam for transmissions based, at least in part,on the pathloss RS, the program instructions are further executable tocause the UE to determine the default beam for transmissions based, atleast in part, on a beam used for a first, last, or indicated pathlossRS in a pathloss RS list configured via radio resource control (RRC)signaling with the base station.
 19. The non-transitory computerreadable memory medium of claim 16, wherein, to determine the defaultbeam for transmissions based, at least in part, on a defaulttransmission beam in another CC, the program instructions are furtherexecutable to cause the UE to determine the default beam fortransmissions based, at least in part, on a default physical downlinkshared channel (PDSCH) beam or a CORESET beam configured in another CC.20. The non-transitory computer readable memory medium of claim 16,wherein the program instructions are further executable to cause the UEto: in response to determining that no CORESESTs and/or TCI states havebeen configured in the CC, determine a pathloss RS for power control fora dedicated physical uplink control channel (PUCCH) or a soundingreference signal (SRS) based, at least in part, on at least one of: adownlink RS used to determine a default spatial relationship; asynchronization signal block (SSB) associated with a most recentrandom-access channel (RACH) procedure in the CC, in a CC in a same bandas the CC, in a CC in a same band group as the CC, or in a CC in a samecell group as the CC; a pathloss RS used for a most recent transmissionon a physical uplink shared channel (PUSCH) in the CC, in a CC in a sameband as the CC, in a CC in a same band group as the CC, or in a CC in asame cell group as the CC; a pathloss RS used for a most recenttransmission of a physical uplink control channel (PUCCH) in the CC, ina CC in a same band as the CC, in a CC in a same band group as the CC,or in a CC in a same cell group as the CC; or a pathloss RS used for amost recent transmission of an SRS in the CC, in a CC in a same band asthe CC, in a CC in a same band group as the CC, or in a CC in a samecell group as the CC.